bpo-28626: rearrange discussion of output formatting to encourage f-strings#6036
Merged
Conversation
nceder
approved these changes
May 14, 2018
nceder
left a comment
nceder
left a comment
Contributor
There was a problem hiding this comment.
I think this improves things in general, as well as adding explanation of f-strings.
Contributor
|
CC @vstinner |
Contributor
Author
|
Shall I go ahead and merge this? |
Member
|
I'm really sorry, I told @nceder that I will review this PR. I read it, but I'm not confortable to approve it. I'm not used to write documentation. @akuchling: If you are confident, sure, please go ahead :-) |
Contributor
|
Thanks @akuchling for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7. |
|
@akuchling: Please replace |
|
GH-8174 is a backport of this pull request to the 3.7 branch. |
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Jul 7, 2018
…trings (pythonGH-6036) The 'output formatting' section of the tutorial talks a lot about manual formatting with things like .rjust() and .zfill(), with only a passing reference to 3.6's new f-strings. This doesn't drop all of the old material, but it does rearrange the topics into a more modern order: f-strings first, discussing formatting specifiers a bit; then calling .format(); finally manual formatting with .ljust(). (cherry picked from commit ced350b) Co-authored-by: Andrew Kuchling <amk@amk.ca>
miss-islington
added a commit
that referenced
this pull request
Jul 9, 2018
…trings (GH-6036) The 'output formatting' section of the tutorial talks a lot about manual formatting with things like .rjust() and .zfill(), with only a passing reference to 3.6's new f-strings. This doesn't drop all of the old material, but it does rearrange the topics into a more modern order: f-strings first, discussing formatting specifiers a bit; then calling .format(); finally manual formatting with .ljust(). (cherry picked from commit ced350b) Co-authored-by: Andrew Kuchling <amk@amk.ca>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Could be backported to 3.7 and 3.6 as well.
https://bugs.python.org/issue28626